Active fault management for metro ethernet service over mpls network

ABSTRACT

In one embodiment, a technique for detecting a break in a pseudowire and automatic shutting down user network interface (UNI) ports affected by the break is provided. In response to the loss of connectivity on the shut down ports, customer edge devices may automatically switch over to redundant circuits (e.g., other UNI ports not affected by the break in the pseudowire) and establish a different pseudowire.

BACKGROUND OF THE INVENTION

1. Field of the Invention

Embodiments of the present invention generally relate to network traffic management.

2. Description of the Related Art

Service providers often offer Layer 2 services over Internet Protocol (IP) based Multi-Protocol Label Switching (MPLS) network cores. As an example, a service provider may offer Metro Ethernet services that provide customers emulated Ethernet connections between distributed customer sites, such as different offices of a business or different campuses of a school or university. The customers of such service providers often require redundant links to the same MPLS core, or maybe even to another Service Provider.

Unfortunately, in the event of a transport failure, identifying and closing customer connections that are affected is a complex process. Further, shutting down affected connections and switching over to redundant connections is a time consuming process that is performed manually.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above recited features of the present invention can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments.

FIG. 1 illustrates an example network topology in accordance with some embodiments of the present invention.

FIG. 2 illustrates a flow diagram of example operations in accordance with some embodiments of the present invention.

FIGS. 3A-3D illustrate example data flow in accordance with some embodiments of the present invention.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Embodiments of the present invention provide active fault management and automatic switchover to redundant paths for applications, such as Metro Ethernet Services. For some embodiments, a fault management system that monitors a network for alarms may take action in the network designed to automatically shut down interfaces affected by a failed transport and cause a switch over to a redundant link.

For some embodiments, the fault management system may detect a break in a pseudowire, determine which customer edge ports in the network are affected by the break, and shutdown the affected ports. In response, the customer edge sites may detect the loss in connectivity resulting from the shutdown of the affected ports and automatically switch over to backup (redundant) circuits. For some embodiments, the fault management system may maintain a database of network topology that allows the customer edge ports that are affected by a transport failure to be identified.

The term pseudowire (PW) generally refers to an emulation of a native service over a Packet Switched Network (PSN), for example, using various encapsulation techniques. A pseudowire effectively emulates the native service as if devices on each end were connected by a single “wire” carrying the native service. The native service may be, for example, ATM, Frame Relay, Ethernet, low-rate TDM, or SONET/SDH. The PSN may be, for example, an MPLS, IP (either IPv4 or IPv6), or L2TPv3 network. In some cases, a pseudowire may provide edge-to-edge connection across a service provider network.

As a result, devices connected by the pseudowire may act as if they are connected via a local Ethernet connection, while they may, in fact be remotely located. Thus, the use of pseudowire connections provides a great deal of flexibility in deploying remote services. However, when a component along a path that forms a pseudowire fails (causing a “break” in the pseudowire) a number of devices can be affected.

As used herein, the term User Network Interface (UNI) generally refers to a point of demarcation between the responsibility of the service provider and the responsibility of the subscriber. As used herein, the term User-Facing provider edge (U-PE) generally refers to the location of a UNI port attachment to customer edge equipment resides, while the term Network-Facing Provider Edge (N-PE) generally refers to the location of a connection to the core.

As used herein, the term Metro Ethernet generally refers to a network based on the Ethernet standard and which covers a metropolitan area. Such networks are commonly used as a metropolitan access network to connect subscribers and businesses to a Wide Area Network (WAN), such as the Internet. Entities, such as businesses and schools, can also use Metro Ethernet to connect branch sites to their own Intranets.

The concept of a Metro Ethernet Virtual Connection (EVC) is defined by MEF 10. A typical service provider Metro Ethernet network is a collection of interconnected Layer 2 or 3 switches and/or routers in any suitable topology (e.g., a ring, hub-and-spoke, full mesh, or partial mesh). The network typically has a hierarchy with a core, distribution and access components. Typically, the core is an existing IP/MPLS backbone, but may migrate to other forms of transport.

In accordance with embodiments of the present invention, a fault management system may be responsible for both determining that a service (e.g., a Metro Ethernet Service) is experiencing a transport problem across its core and taking action designed to cause customer edge components to switch to backup circuits (e.g., to a different UNI port), effectively switching to a different pseudowire. Such actions may include sending messages to disable (bring down) a UNI port affected by a broken pseudowire.

Such a fault management system may work with point-to-point EVC over IP/MPLS core to provide the services described herein. The point-to-point EVC, sometimes referred to as a Virtual Private Wire Service (VPWS), typically defines two types of Metro Ethernet services: Ethernet Relay Service (ERS) with one VLAN and Ethernet Wire Service (EWS).

An Exemplary Network Architecture

FIG. 1 illustrates an example network architecture in which embodiments of the present invention may be utilized. The architecture may enable services, such as Metro Ethernet services, or emulation of some other type of transport services (e.g., Frame Relay or ATM), to connect remotely located customer sites 120. In addition to supporting a single service, the architecture may also allow for the interworking of any heterogeneous combination of services, for example, between Ethernet and Frame Relay or ATM services, supporting the transport of customer traffic from a wide variety of sources. As an example, there may be Ethernet service on the customer side of the core and ATM on the service provider side.

The architecture generally includes a service provider network 110 that routes network traffic (e.g., of data, voice, and the like) between various customer sites 120. While not shown, those skilled in the art will appreciate that the provider network 110 may also include a “fabric” of intermediate network devices, such as switches and routers, to route and support traffic between the PE routers 112. The sites 120 may include sites from different entities (e.g., schools or businesses), as well as multiple sites from the same entity (e.g., regional branch offices or headquarters of a business or different campuses of a school).

For some embodiments, the service provider network 110 may be a Multiprotocol Label Switching (MPLS) network that forwards internet protocol (IP) traffic using labels. These labels may instruct the routers and the switches in the provider network 110 where to forward packets as they are routed between PE routers 112 en route to CEs 122 at the customer sites 120 based on pre-established IP routing information. Further, for some embodiments, customer sites may be linked through more than one service provider network, for example, to provide redundancy for critical applications.

Access domains 116 may be established, that serve as an interface between customer sites and the service provider network 110. For example, CE routers 122 may connect, via an Ethernet connection (e.g., Copper-100BASE-TX, or fiber-100BASE-FX), to UNI ports of user facing PE (U-PEs) routers 118 that receive and transport customers' Ethernet packets over the (e.g., MPLS) service provider network 110. The UNI ports may comprise a variety of different type access circuits, such as Ethernet of Frame Relay and the same architecture may support both.

As illustrated, the illustrated architecture thus enables the establishment of a pseudowire 115 that provides emulation of services between customer sites. As illustrated, a CE 122 may establish redundant paths to the service provider network 110, for example, by maintaining inactive links to UNI ports in the U-PEs. In the illustrated figure, an inactive link is shown as a dashed line. As will be described in greater detail below, in the event a transport failure causes a failure of service (a “break” in the pseudowire), affected UNI port connections may be brought down, prompting an automatic switchover at the CE to redundant links.

For example, a network management system (NMS) 130 may be configured to detect a break in the pseudowire 115 and identify which UNI ports are affected by correlation using network topology information. In response to detecting a break, the NMS 130 may dispatch messages to the U-PEs designed to shut down the affected ports. As a result, the CEs may automatically switch over to a different UNI port connection, establishing a different pseudowire.

In general, the NMS 130 may be configured to monitor performance of the provider network 110, as traffic is exchanged over the network. The NMS 130 may be implemented, for example, at a network operation center. The NMS 130 may poll components in the provider network 110 and/or may communicate with agents (e.g., network probes) deployed in the provider network 110 in an effort to detect breaks in a pseudowire.

For example, a network probe deployed at a device along a pseudowire may be configured to automatically send a trap to the NMS 130 upon detection of a significant event, such as a loss in connectivity or the reduction in service level above or below specified threshold amount. In response, the NMS 130 may consult a network topology database 132 in an effort to identify UNI ports affected by the break.

For some embodiments, the network topology may be discovered utilizing a specialized protocol, such as the Cisco Discovery Protocol (CDP) established by Cisco Systems Inc., that allows network devices (switches, routers, access servers, bridges, and the like) to advertise its existence to other devices and receive information about other devices on the same network. Topology information gathered in the discovery phase may be used to populate the network management database 132 at NMS 130. This topology information may include information about pseudowire and UNI port relationships that may be used to automatically shut down UNI ports affected by a break in a pseudowire.

FIG. 2 illustrates example operations 200, that may be performed to automatically shutdown UNI ports affected by a break in a pseudowire and prompt a switchover to a backup link. Some of the operations 200 (e.g., operations 202-206) may be performed by the NMS 130, while other operations (e.g., operation 208) may be performed by a CE router 122. The operations 200 may be described with reference to FIGS. 3A-3D, which illustrate different states of the Metro Ethernet of FIG. 1 at different states.

The operations begin, at 202, by detecting a break in a pseudowire. For example, as illustrated in FIG. 3A, a break 117 in the pseudowire 115 may be detected by PEs 112. In response, the affected PEs may send traps to the NMS 130. Based on the receiving of these traps, the NMS 130 can determine that a Pseudo-wire is up or down. For some embodiments, the state of a pseudo-wire may also be determined by polling.

At 204, the NMS 130 determines which UNI ports are affected by the broken pseudowire. For example, with knowledge of the topology of the service architecture (e.g., gained from provisioning or through discovery), the NMS 130 may be able to determine which U-PE/UNI port is actually using the broken pseudo-wire. As illustrated in FIG. 3B, the NMS 130 may access the topology database 132 to access topology information and determine which UNI ports in the network are affected by the identified pseudowire.

At 206, the NMS 130 shuts down the affected UNI ports. For example, as illustrated in FIG. 3C, the NMS 130 may be configured to automatically send a command to the U-PEs on which the affected UNI ports reside, instructing them to shut down those ports, resulting in a loss of connectivity between the corresponding CEs (as indicated by the dashed lines). Because the underlying service is no longer available to the customers on these ports due to the transport failure 117, shutting these ports down may allow the CEs to switch over to redundant circuits with minimal impact to the customer.

At 208, in response to detecting the loss in connectivity, the CEs may automatically switch over to backup circuits. For example, as illustrated to FIG. 3D, the CEs may automatically switch over to the redundant links established via connection with different UNI ports that are not affected by the transport failure 117. With these redundant links active (as indicated by the change to solid lines), a different pseudowire 415 that avoids the transport failure 117 may be established between the CEs.

By automatically detecting transport failures and taking action to shut down affected UNI ports, the need for customers to manually re-configure their switches in the event of a connectivity outage across the network core. Shutting down the affect ports prompts an automatic switch over to a redundant link.

While the foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow. 

1. A method comprising: receiving data related to a transport failure in a first path of a packet-switched network used to establish a pseudo-wire connection between at least two devices; determining user network interface (UNI) ports used to connect the devices to the network that are affected by the transport failure; and sending one or more messages to one or more devices on which the affected UNI ports reside to disable one or more of the affected UNI ports.
 2. The method of claim 1, wherein determining UNI ports used to connect the devices to the network that are affected by the transport failure comprises: querying a database containing network topology information.
 3. The method of claim 2, further comprising: discovering the network topology information through messages sent from components in the network; and populating the database with the discovered information.
 4. The method of claim 1, wherein the at least two devices comprise at least one customer edge device.
 5. The method of claim 1, wherein at least one of the one or more messages are designed to disable an affected UNI port and cause a device connected to the affected UNI port to switch over to a backup UNI port.
 6. The method of claim 1, wherein the UNI ports comprise one or more Ethernet UNI ports.
 7. The method of claim 1, wherein the UNI ports comprise at least one of: one or more Asynchronous Transfer Mode (ATM) UNI ports and one or more Frame Relay UNI ports.
 8. The method of claim 1, wherein the network comprises a Multi-Protocol Label Switching (MPLS) network.
 9. A network management system, comprising: a database for storing topology information for a network used to establish a pseudo-wire connection between at least two devices; fault management logic configured to detect a transport failure in a first path of the network used to establish a pseudo-wire connection between at least two customer edge devices; correlation logic configured to determine one or more user network interface (UNI) ports used to connect the customer edge devices to the network that are affected by the transport failure; and failover logic configured to send one or more messages to one or more devices on which the affected UNI ports reside to shut down one or more of the affected UNI ports.
 10. The network management system of claim 9, wherein the correlation logic is configured to determine affected UNI ports by querying a network topology database.
 11. The network management system of claim 9, wherein the at least two devices comprise at least one customer edge device.
 12. The network management system of claim 9, wherein at least one of the one or more messages are designed to disable an affected UNI port and cause a device connected to the affected UNI port to switch over to a backup UNI port.
 13. The network management system of claim 9, wherein the UNI ports comprise one or more Ethernet UNI ports.
 14. The network management system of claim 9, wherein the first set of UNI ports comprises at least one of: one or more Asynchronous Transfer Mode (ATM) UNI ports and one or more Frame Relay UNI ports.
 15. A system, comprising: user network interface (UNI) ports for connecting devices to a packet switched network used to establish a pseudo-wire connection between at least two devices; and a network management system having fault management logic configured to detect a transport failure in a first path of the network used to establish the pseudo-wire connection, correlation logic configured to identify UNI ports used to connect the at least two devices to the network that are affected by the transport failure, and failover logic configured to send one or more messages to devices on which the affected UNI ports reside to shut down one or more of the affected UNI ports.
 16. The system of claim 15, wherein the correlation logic is configured to determine affected UNI ports by querying a network topology database.
 17. The system of claim 15, wherein the at least two devices comprise at least one customer edge device.
 18. The system of claim 15, wherein at least one of the one or more messages are designed to disable an affected UNI port and cause a device connected to the affected UNI port to switch over to a backup UNI port.
 19. The system of claim 15, further comprising: one or more UNI ports usable to connect the devices to the network to establish a different pseudowire connection between the devices that is not affected by the transport failure.
 20. The system of claim 15, wherein the packet switched network is a Multi-Protocol Label Switching (MPLS) network.
 21. The system of claim 15, wherein the UNI ports comprise one or more Ethernet UNI ports.
 22. The system of claim 15, wherein the UNI ports comprise at least one of: one or more Asynchronous Transfer Mode (ATM) UNI ports and one or more Frame Relay UNI ports. 